Cargo Detail

1. Overview

Cargo Detail is a child table Doctype within the VSD Fleet MS module. It stores detailed information about each cargo item associated with a Cargo Registration. This includes container size, cargo type, package counts, route details, loading/unloading locations, and associated service charges.

2. Key Features

• Stores detailed cargo information at a granular level.
• Supports different container sizes including Loose cargo and standard container sizes (20 FT, 40 FT).
• Auto-fetches related data from linked Manifest and Trip documents.
• Captures cargo location and destination details.
• Maintains service charge details linked to sales invoices.
• Enables assigning manifests dynamically via button.
• Tracks assigned drivers, trucks, and transporter types automatically.

3. Pre-Requisites

• VSD Fleet MS module installed in Frappe/ERPNext environment.
• Related DocTypes such as Manifest, Trip Routes, Cargo Types, Transport Location, and Sales Invoice properly set up.
• Naming series configured for Cargo Detail (Cargo-.YY.-.).
• User must have permission to access Cargo Registration and its child tables.

4. Step-by-Step Usage

1. Open a Cargo Registration document.
2. In the Cargo Details child table, add new entries describing individual cargo items.
3. Select the container size (Loose, 40 FT, 20 FT).
4. Fill in container number and seal number if container is not Loose.
5. Enter number of packages and net weight.
6. Specify cargo loading and destination countries and cities.
7. Set expected loading and offloading dates.
8. Link the appropriate cargo route.
9. Assign service charges by selecting service item, currency, and rate.
10. If no manifest assigned, use the Assign Manifest button to link a manifest.
11. Upon manifest assignment, assigned drivers, trucks, and transporter details auto-populate.
12. Save and submit the Cargo Registration as needed.

5. Script Customizations

The backend Python class is minimal and only extends the base Document:

from frappe.model.document import Document

class CargoDetail(Document):
    pass
## 6. Troubleshooting (Common Errors and Resolutions)

| Issue                        | Possible Cause                          | Resolution                                                        |
|------------------------------|---------------------------------------|------------------------------------------------------------------|
| Cannot assign manifest        | Manifest already assigned or missing cargo ID | Ensure cargo ID exists before assigning manifest. Verify manifest availability. |
| Container number not visible  | Container size set to Loose            | Container number field only appears if container size is 20 FT or 40 FT. Change container size to enable. |
| Auto-fetch fields not updating| Manifest not linked or saved           | Save manifest details and reload Cargo Registration. Check link field correctness. |

---

## 7. User Roles and Permissions

- Users with permission to **Cargo Registration** can add or edit cargo details.
- Read-only fields such as assigned driver/truck are fetched from Manifest and cannot be edited directly.
- Only authorized roles can assign manifests using the button.

---

## 8. Key Notes

- The `naming_series` ensures unique cargo detail IDs with a yearly sequence.
- Cargo details act as a child table, so they cannot exist independently.
- Manifest assignment is essential for linking cargo to transport logistics.

---

## 9. What Business Process Pain Point Does It Help 

- Eliminates manual tracking of multiple cargo items within a shipment.
- Automates linkage between cargo, manifests, trips, and billing processes.
- Reduces errors in cargo documentation by enforcing required fields and dependencies.
- Service charges tie into accounting via Sales Invoices.